Transaction management system providing payment functionality between mobile devices and token identifier devices

ABSTRACT

A method and system support payments between two entities using a mobile device and a token identifier device. A payment or gratuity action is initiated by a payer using their mobile device, such as mobile communication handset, to scan a token identifier stored in the payee&#39;s token identifier device. In one example, the token identifier device is an RFID or NFC type device. After the token identifier is obtained, the mobile device communicates the TokenID, gratuity amount, and payer authentication information to a transaction management system that validates and attempts to transfer funds between the two entities. In one example, the transaction management system is a server system that communicates over a TCP/IP network. The transaction management system sends a communication to the mobile device indicating whether or not the transfer was successful.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit under 35 U.S.C. § 119 of U.S.provisional patent application Ser. No. 62/742,315, entitled“Transaction Management System Providing Payment Functionality BetweenMobile Devices And Token Identifier Devices,” filed on Oct. 6, 2018. Thesubject matter of U.S. provisional patent application Ser. No.62/742,315 is incorporated herein by reference.

TECHNICAL FIELD

The described embodiments relate generally to mobile payments.

BACKGROUND INFORMATION

Gratuities or tips are often paid to people in recognition of theirdiligence or contribution. Food-related establishments, entertainmentestablishments, and lodging establishments often provide services orhave service providers who are paid with tips. In addition, patrons mayalso wish to contribute charitable donations. Some services, such asWiFi, ought to be provided in exchange for payment but the fees are toominimal to justify having a mechanism in place to collect fees. Otherservices include valet services, attendants, and hotel maids. Often inthese circumstances, patrons do not have cash readily available.Tourists also often do not have an opportunity to convert money intolocal currency. A more robust solution is desirable.

SUMMARY

A method and system support payments between two entities using a mobiledevice and a token identifier device. A payment or gratuity action isinitiated by a payer using their mobile device, such as mobilecommunication handset, to scan a token identifier stored in the payee'stoken identifier device. In one example, the token identifier device isan RFID or NFC type device. After the token identifier is obtained, themobile device communicates the token identifier (TokenID), gratuityamount, and payer authentication information to a transaction managementsystem that validates and attempts to transfer funds between the twoentities. In one example, the transaction management system is a serversystem that communicates over a TCP/IP network. The transactionmanagement system sends a communication to the mobile device indicatingwhether or not the transfer was successful. If, for example, the firstentity does not have sufficient funds, then the transfer will fail, butif the first entity does have sufficient funds, then the funds will betransferred to the second entity.

Before initiating transfers, the payee and payors are registered withthe transaction management system. Payment identification, payer'smobile device authentication, and payee's registered TokenID(s) areregistered with the transaction management system. This enables thetransaction management system to maintain, receive, and process thepayee payment push requests. The payee's TokenIDs are then distributedat the payees' business location or other appropriate locations. Becausethe TokenIDs are inexpensive and registered only to the payee, maintainno theft value and thus maybe left unattended.

The instant system provides substantial advantages over visual code orQR code payment systems. Such conventional QR code exchange systems areoften difficult for users to use and result in frustrating experiences.QR code exchange systems employs different process that becomescumbersome to the user because a visual scan must be precisely align.Additional hardware, such as a camera, is involved. The camera mustdecode the characters embedded in the image. If there is a mark ordamage on the visual code, then the transaction cannot be carried outsuccessfully. In addition, if there is a smudge on the lens of thecamera, then the scan will not be accurate. QR code exchange systemstake on damage, wear out, and need to be replaced. The instant system,on the other hand, employs NFC in one embodiment and can be encapsulatedin a very thick plastic material that provides protection from theenvironment. This provides a significantly more reliable system.

In addition, the instant system provides seamless transactions providingsignificant advantages to the user's interactive experience with thesystem. By tapping the mobile device on the token identifier device, asimple and singular user action, the system triggers the exchange:immediate scanning of the token code and communication with a remotetransaction system that initiates the transfer of funds. Because paymenttransactions can be triggered by physical gesture, such as tapping themobile device on the token identifier device, the transaction managementsystem, mobile device, and token identifier device form part of what isalso referred to as the “TipTap Network”.

In accordance with another novel aspect, each party registered with thesystem maintains the security of their financial information. Nosensitive user payment data is shared outside the user phone or theTipTap Network. Only the payee can authorize funds to leave theiraccount. The instant system provides a transfer of payment withoutjeopardizing security or risking financial information being obtained bymalicious entities. Additionally, once the token identifier isregistered to and associated with a user, the token identifier is lockedto that user. The token identifier cannot be taken away from that userunless the user gives permission by intentionally unlocking the token.

In accordance with yet another novel aspect, the token identifier deviceis extremely low cost, durable, and adaptable. Each token identifierdevice costs a fraction of a typical POS terminal to the point of beingdisposable. The token identifier device is conformable to any physicalshape that is aesthetically pleasing or designed for marketing purposes.For example, the token identifier device may be embedded in a poster, aflier, a business card, or other paper marketing related material. Thetoken identifier device may be embedded in a good or product thatcorresponds to the circumstances of the transaction, for example, thetoken identifier device may be embedded in a guitar case or in a tipjar. In another embodiment, the token identifier device is embedded in awearable, for example, the token identifier is embedded in a bracelet, anecklace, a ring, a badge, or a tipping hat.

In addition to handling payments between users, the transactionalmanagement system can securely perform predetermined functions after thetransfer is validated. In one embodiment, after payment is validated,the system triggers a mechanical or digital action. For example, afterpayment validation, the system causes a network connected robot or anIoT (Internet of Things) device to do some work for the user, such asmake a cup of coffee, clean a restroom, wash a vehicle, or perform otherrobot-work related functions. In another example, after payment isvalidated, the system causes a network connected machine to vend a soda,open a parking garage gate, dispense water, play a song on a juke box,provide photocopies or scanner function, or operate photo booths. In yetanother example, after payment is validated, the system causes anotherphone operated by a recipient of funds to offer access into a venue,such as a bar or club, or provide a special recognition for havingdonated like a pin or a sticker. In yet another example, after paymentis validated, the system acknowledges a payment for publictransportation and permits the user to travel. The transactionmanagement system can also be used to facilitate a silent auction whereindividuals view various items up for auction and tap their phones ontoken devices associated with auction items to adjust their bids. Thetransaction management system can also be used to provide information orcredentials to access information in exchange for payments, such asWiFi, brochures, or tourist information. The transaction managementsystem can also be used to pair two devices in exchange for payment,such as pairing over Bluetooth or WiFi. The transaction managementsystem can also be used to reserve a public space, conference room, oropen a public bathroom. The transaction management system eases the flowof money thereby enabling better use of community resources andincreasing social benefits.

In another embodiment, a second entity, such as a service providerentity, obtains a token identifier device having a token ID. The tokenID is supplied to a transaction management system. Next, the secondentity configures selectable options, such as a menu, with thetransaction management system. Next, a first entity, such as customerentity, obtains the token ID from the token identifier device. Next, thetoken ID is communicated from the device to the transaction managementsystem. Next, the transaction management system responds by supplyingthe selectable options to the user device. Next, transaction informationis communicated from the user device to the transaction managementsystem. Next, the transaction information is supplied to the serviceproviding entity. The service providing entity performs functions inaccordance with the transaction information. Next, transaction and/ororder confirmation is supplied from the transaction management system tothe user device. In one example, the first entity and second entityinteract with the transaction management system and perform the abovefunctions via a mobile application that is provided by an entity thatmanages the transaction management system.

Further details and embodiments and methods are described in thedetailed description below. This summary does not purport to define theinvention. The invention is defined by the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, where like numerals indicate like components,illustrate embodiments of the invention.

FIG. 1 is a flowchart of a method 100 in accordance with one novelaspect.

FIG. 2 is a diagram that shows how a first entity provides paymentinformation onto a mobile device.

FIG. 3 is a diagram that shows how a token identifier is obtained fromthe token identifier device of the second entity and is registered withthe mobile device of the first entity.

FIG. 4. is a diagram that shows how a mobile device communicates paymentinformation and a token identifier to the transaction management system.

FIG. 5 is a diagram that shows how the transaction management systemsends a confirmation communication to the mobile device indicatingwhether or not the payment was successful.

FIG. 6 is a diagram that shows how the first entity and second entityregister and setup their accounts with the transaction managementsystem.

FIG. 7 is a block diagram of the structure of the mobile device and thetoken identifier device.

FIG. 8 is a diagram that shows various additional account featuresprovided by the transaction management system.

FIG. 9 is a diagram of a landing page on the mobile device after user(payor) login credentials are validated by the transaction managementsystem.

FIG. 10 is a diagram that shows the mobile device scanning anenvironment for token identifier devices.

FIG. 11 is a diagram that shows a user profile page of the payee that ispresented to the user (payor) after money is transferred.

FIG. 12 is a diagram that shows a user setting sliding panel overlay.

FIG. 13 is a diagram that shows a list of user profiles of users thatare registered with the transaction management system.

FIG. 14 is a diagram that shows payment settings of the user.

FIG. 15 is a diagram that shows how token identifiers are configured.

FIG. 16 is a diagram that shows transaction history of a user.

FIG. 17 is a diagram of another embodiment of a transaction managementsystem 230.

FIG. 18 is a detailed diagram of the transaction management system 230.

FIG. 19 is a flowchart of a method 300.

FIG. 20 is a flowchart of a method 400.

FIG. 21 is a flowchart of a method 500.

FIG. 22 is a flowchart of a method 600.

DETAILED DESCRIPTION

Reference will now be made in detail to some embodiments of theinvention, examples of which are illustrated in the accompanyingdrawings.

FIG. 1 is a flowchart of a method 100 in accordance with one novelaspect. In a first step (step 101), a first entity provides paymentinformation onto a mobile device. In one example, the first entity is aperson who desires to pay a gratuity to another person. For example, inFIG. 2 a first entity 110 or payor having a mobile device 111 desires totransfer money to another entity. The mobile device 111 is a mobilecommunication handset, a tablet, or other device capable ofcommunicating over a network. The first entity 110 enters paymentinformation, for example, the amount of money to be transferred. In thisexample, first entity 110 enters “$2.00” onto the user interfacepresented on the display of the mobile device.

In a second step (step 102), the first entity obtains a token identifierfrom a token identifier device and registers the token identifier withthe mobile device. The token identifier is associated with a secondentity that is to receive payment from the first entity. In one example,the token identifier is obtained wirelessly. In another example, thetoken identifier is obtained by optically scanning a visual code. In yetanother example, the first entity supplies the token identifier onto themobile device. In the example of FIG. 3, the second entity 120 or payeehas a token identifier device 121. The second entity 120 desires toreceive money as appreciation for his/her musical abilities. In thisexample, the second entity 120 is a piano player.

To initiate the transfer, the first entity 110 brings mobile phonewithin a pre-determined distance, typically of less than 1-2 cm of thetoken identifier device 121. The first entity physically taps theirmobile phone onto the token identifier device 121. Circuitry within themobile device 111 generates energy that is detected and absorbed by thetoken identifier device 121. This energy causes the token identifierdevice 121 to be activated. Depending on the type of token identifierdevice employed, a handshake may occur. For example, if the tokenidentifier device 121 is a Near Field Communication (NFC) token, then ahandshake occurs between the mobile device 111 and the token identifierdevice 121. If the token identifier device 121 is a Radio FrequencyIdentification (RFID) device, then no handshake occurs. After the tokenidentifier device 121 is activated, the circuitry within the mobiledevice 111 obtains the token identifier 122 from the token identifierdevice 121. At this point, haptic feedback in the form of a vibration ora sound from the phone would indicate to the first entity that the scanoccurred successfully. The token identifier 122 is registered onto themobile device 111. In this example, the token identifier 122 is a string“D83HDNX1”.

In accordance with another novel aspect, the token identifier device 121is not coupled to any dedicated power source and is significantly lowcost. Unlike traditional point of sale (POS) terminals which require adedicated power source, such as a power supply or battery, the tokenidentifier device 121 does not require any dedicated power. The tokenidentifier 121 is an extremely low-cost device providing a commerciallycheap way for entities to obtain and receive payments. In typicaltransactions involving POS terminals and mobile devices, the POSterminal is powered by a dedicated power supply. The POS terminalincludes an NFC module or other wireless mechanism that communicateswith the mobile device. In such conventional transactions, the POSterminal communicates financial information related to the transaction,such as a payment amount. The mobile device receives the transactioninformation and confirms with a financial institution that the owner ofthe mobile device has the requisite funds to complete the transaction.Once confirmed, the mobile device communicates encrypted financialinformation to the POS terminal and the POS terminal completes thetransaction.

On the other hand, the novel token identifier device 121 does notcommunicate any financial information to the mobile device 111. Themobile device 111 also does not communicate any financial information tothe token identifier device 121. The only information communicated fromthe novel token identifier device 121 to the mobile device is the tokenidentifier 122. The mobile device 111 does not communicate anyinformation to the token identifier device 121. No sensitive informationis exchanged between the mobile device 111 and the token identifierdevice 121.

In a third step (step 103), the mobile device communicates the paymentinformation and the token identifier to a transaction management systemthat attempt a transfer from the first entity to the second entity inaccordance with the payment information. For example, in FIG. 4 themobile device 111 communicates the payment information 112 (“$2.00”),security credentials (a userID “1111”) of the first entity 110, and thetoken identifier 122 (“D83HDNX1”) to the transaction management system130. the transaction management system 130 uses this information toattempt to transfer funds from the first entity 110 to the second entity120. In this example, the security credentials correspond to the userID“1111” of the first entity 110. It is understood that this is asimplified example presented for explanatory purposes. In actualimplementation, the security credentials would not be a simple string,but would be realized using industry standard authentication methods,such as OAuth 2.0.

The transaction management system 130 comprises a processor 131, astorage device 132, a network interface 133, and a communication bus134. Network interface circuit 133 is configured to communicate dataacross network 140. The storage device 132 stores account informationfor users, including payors and payees. Reference numeral 135 identifiesa table associated with payors. Reference numeral 136 identifies a tableassociated with payees. It is understood that a user may be both a payorand a payee depending on the type of financial activity the user engagesin.

The mobile device 111 comprises input hardware 114, display 115,transaction circuit 117, and a network interface circuit 118. Thenetwork interface circuit 118 is configured to communicate data acrossnetwork 140. The transaction circuit 117 comprises a controller 118, anamount of memory that stores the token identifier 122 obtained from thetoken identifier device 121, and payment information 112 provided by thefirst entity 110.

In a fourth step (step 104), a determination is made whether thetransfer between the first entity 110 and the second entity 120 wassuccessful. If the transfer is determined to have been successful, thenthe method proceeds to a fifth step (step 105). For example, in FIG. 5 adetermination is made that the first entity 110 has sufficient funds inhis/her account with an available balance of $10.00. Thus $2.00 aretransferred from the account of the first entity 110 to the account ofthe second entity 120. Confirmation communication 142 indicate thatpayment was successful.

If, on the other hand, the transfer is determined to have failed, thenthe method proceeds to a sixth step (step 106). Although not illustratedin FIG. 5, if the first entity 110 had only $1.00 in his/her account,then the transfer would have failed and confirmation communication 142would have reflected failure.

FIG. 6 is a diagram that shows how the first entity and second entityregister and setup their accounts with the transaction management system130. The first entity 110 registers his/her account with the transactionmanagement system 130 by creating an account, configuring financialinformation, and registered the mobile device(s). Configuring financialinformation involves transferring funds to the transaction managementsystem 130 or providing a link between the transaction management system130 and an account at a banking institution associated with the firstentity 110. These funds are used to transfer to other entities.

The second entity 120 registers his/her account with the transactionmanagement system 130 by creating an account, configuring financialinformation, and registering token identifier devices. Configuringfinancial information involves providing a link between the transactionmanagement system 130 and an account at a banking institution associatedwith the first entity 110. This information is used to transfer moneyfrom the payees' account to an outside account associated with thesecond entity 120. Token registration involves the second entity 120supplying the token identifier to the transaction management system 130and associating that token identifier for each device with the accountof the second entity 120.

FIG. 7 is a block diagram of the structure of the mobile device 111 andthe token identifier device 121. The mobile device 111 includes aprocessor or controller circuit, Radio Frequency (RF) circuitry, and anantenna or coil. The processor controls the RF circuitry. The RFcircuitry uses the antenna to obtain the token identifier from the tokenidentifier device 121.

The token identifier device 121 comprises an antenna or coil and tokenidentifier circuitry. In one example, the token identifier circuitryincludes a processor and an amount of non-volatile memory. In anotherexample, the token identifier circuitry includes no processor. In yetanother example, the token identifier device 121 includes a battery orcapacitor used to supply circuitry internal to the token identifierdevice 121.

When the mobile device 111 is brought within a pre-determined distanceof the token identifier device 121, energy output from antenna or coilof the mobile device 111 is detected and absorbed by the antenna or coilof the token identifier device 121. This absorbed energy is sufficientto activate the token identifier circuitry within the token identifierdevice 121. Once activated, the mobile device 111 wirelessly reads thetoken identifier stored within the token identifier circuitry of thetoken identifier device 121.

FIG. 8 is a diagram that shows various additional account featuresprovided by the transaction management system 130. For example, usersmay message other users registered with the transaction managementsystem 130, view payment history, share payment history with others,save payee information, manage advertisement campaigns, events, anddonation drives, modify security settings, modify username and passwordsettings, upload images or profile pictures, modify user information andadvertising content, manage payment settings, and register additionaltokens.

FIG. 9 is a diagram of a landing page on the mobile device after user(payor) login credentials are validated by the transaction managementsystem. The mobile device is running a mobile application configured tocommunicate with the transaction management system and with NFCcircuitry of the mobile phone that scans token identifier devices. Thelanding page includes a tip button, preset user tip amounts, andhorizontal slider of tip amounts that provide the user functionality toenter a desired tip amount.

FIG. 10 is a diagram that shows the mobile device scanning anenvironment for token identifier devices. After the tip button isactivated, the mobile phone enters a scan mode and the NFC antenna isenabled. While the scan mode is active, if the phone is brought withinproximity of the token identifier device, then the token ID stored bythe token identifier device is immediately scanned. Once the token ID isscanned, the transaction is initiated and funds are transferred from theuser (mobile phone owner) to the payee (token identifier device owner).

FIG. 11 is a diagram that shows a user profile page of the payee that ispresented to the user (payor) after money is transferred. Once thetransaction is completed, the user (payor) is directed to the profilepage of the payee. Here, the user (payor) can add, follow, save, block,tip again, view feed, and/or send messages to the payee.

FIG. 12 is a diagram that shows a user setting sliding panel overlay.This panel is activated by swiping right on the left side of the screen.This overlay provides the user options to view or edit their ownprofile, add bank cards, add or edit their token identifiers, viewpayment history of received or sent payments, edit settings such aslogin credentials and notification settings, and transfer funds to otherbanking institutions such as their personal checking account.

FIG. 13 is a diagram that shows a list of user profiles of users thatare registered with the transaction management system. Here, users cansearch for other users registered with the system, scroll throughfollowed users, and follow new users. Selecting a user on the listdirects the user to the corresponding user profile of the selected user.

FIG. 14 is a diagram that shows payment settings of the user. Bank cardsor ACH can be added, modified or deleted. In addition, funds can bedeposited or withdrawn.

FIG. 15 is a diagram that shows how token identifiers are configured. Alist of token identifiers registered to the user are presented. Here,the user is presented with options to delete, add, view, and/or lock orunlock token identifiers.

FIG. 16 is a diagram that shows transaction history of a user. Thereuser is presented with a List of all tips received and sent. Optionalfilters are provided that provide searching of transfers by date,location, amounts, or users.

FIG. 17 is a diagram of another embodiment of a transaction managementsystem 230. First (#1), a second entity 220, such as a service providerentity, obtains a token identifier device having a token ID. The tokenID is supplied to the transaction management system 230. Next (#2), thesecond entity 220 configures selectable options, such as a menu, withthe transaction management system 230. In the case of a service providerthat provides food, the selectable options are a menu. A serviceprovider may choose to register multiple different token identifiers andhave different types of menu items associated with different token IDs.For example, a service provider with an extensive drink menu mayregister a token ID with only drinks options and register another tokenID with only food options.

Next (#3), a first entity, such as customer entity obtains the token ID122 from the token identifier device 121. In one example, the token ID122 is obtained by “tapping” their mobile device against the tokenidentifier device 121. In another example, the customer entity 210 readsthe token ID 122 and inputs the token ID directly into their device. Inanother example, the customer entity 210 scans a visual code (e.g., QRcode) on the token identifier device 121. Next (#4), the token ID iscommunicated from the device to the transaction management system 230.Next (#5), the transaction management system 230 responds by supplyingthe selectable options to the user device. In one example, thetransaction management system 230 performs a lookup to obtain theconfigured selectable options associated for that particular token ID.Next (#6), transaction information is communicated from the user deviceto the transaction management system 230. In one example, thetransaction information includes the selected items and the quantity ofeach. Next (#7), the transaction information is supplied to the serviceproviding entity 220. The service providing entity 220 performsfunctions in accordance with the transaction information. Next (#8),transaction and/or order confirmation is supplied from the transactionmanagement system 230 to the user device.

FIG. 18 is a detailed diagram of the transaction management system 230.The transaction management system 230 comprises a processor 231, astorage device 232, a network interface 233, and a communication bus234. Network interface circuit 233 is configured to communicate dataacross network 140. The storage device 232 stores account informationfor users, including payors and payees, selectable options, andtransaction information. Reference numeral 235 identifies tables inwhich the customer entity 210 information is stored within the storagedevice 232. Reference numeral 236 identifies tables in which the serviceprovider entity 220 information is stored within the storage device 232.Reference numeral 237 identifies tables in which the transactioninformation is stored within the storage device 232.

FIG. 19 is a flowchart of a method 300. In a first step (step 301), atoken identifier is communicated from a device to a transactionmanagement system. In a second step (step 302), selectable options arereceived from the transaction management system onto the device. Thetransaction management system uses the token identifier to generate theselectable options. In a third step (step 303), transaction informationis communicated from the mobile device to the transaction managementsystem. The transaction information is configured using the selectableoptions received from the transaction management system.

FIG. 20 is a flowchart of a method 400. In a first step (step 401), atoken identifier is associated with a plurality of selectable options ona transaction management system. In a second step (step 402), a tokenidentifier communication is received from a device onto the transactionmanagement system. In a third step (step 403), selectable options areprovided from the transaction management system to the device based onthe token identifier communication. In a fourth step (step 404),transaction information is received from the device onto the transactionmanagement system. the transaction information includes selected itemsfrom the selectable options provided to the device.

FIG. 21 is a flowchart of a method 500. The method 500 includes anescrow step in which the transaction management system provides escrowfunctionality between the first entity and the second entity. The firstentity can supply the funds held in escrow by the entity providing thetransaction management system. Once both the first and second entityunlock the escrow, then the funds are transferred to the second entity.

In a first step (step 501), a token identifier is associated with aplurality of selectable options on a transaction management system. In asecond step (step 502), a token identifier communication is receivedfrom a device onto the transaction management system. In a third step(step 503), selectable options are provided from the transactionmanagement system to the device based on the token identifiercommunication. In a fourth step (step 504), transaction information isreceived from the device onto the transaction management system. thetransaction information includes selected items from the selectableoptions provided to the device. In a fifth step (step 505), fundsassociated with the transaction information are held in escrow untiltransaction management system receives unlock communication.

FIG. 22 is a flowchart of a method 600. The method 600 involves using atransaction management system to replace a point of sale (POS) terminal.POS terminals tend to be costly, space consuming, and haveadministrative and maintenance costs. It is common for service providersto be “offline” thereby disrupting their ability to accept payment andtake new orders. Use of the novel method 600 significantly reduces costsassociated with conventional POS terminals overcomes many operationalproblems associated with POS terminals.

In a first step (step 601), a point of sale (POS) terminal is replacedwith a token identifier device that stores a token identifier. In oneexample, the token identifier device is a sticker with no electronicsand a visual code or text with the token ID. In another example, thetoken identifier device is a device scannable by a mobile device thatstores the token ID. In a second step (step 602), the token identifieris associated with a plurality of selectable options on a transactionmanagement system. In a third step (step 603), a token identifiercommunication is received from a device onto the transaction managementsystem. In a fourth step (step 604), selectable options are providedfrom the transaction management system to the device based on the tokenidentifier communication. In a fifth step (step 605), transactioninformation is received from the device onto the transaction managementsystem. The transaction information includes selected items from theselectable options provided to the device.

Although the present invention has been described in connection withcertain specific embodiments for instructional purposes, the presentinvention is not limited thereto. For additional details on thestructure on function of the system and method described above, see:U.S. provisional patent application Ser. No. 62/742,315, entitled“Transaction Management System Providing Payment Functionality BetweenMobile Devices And Token Identifier Devices,” filed on Oct. 6, 2018, andwhich is hereby incorporated by reference. Accordingly, variousmodifications, adaptations, and combinations of various features of thedescribed embodiments can be practiced without departing from the scopeof the invention as set forth in the claims.

What is claimed is:
 1. A method comprising: activating a tokenidentifier device using a mobile device, wherein in response toactivating the token identifier device, the mobile device wirelesslyobtains a token identifier stored in the token identifier device;communicating the token identifier from the mobile device to atransaction management system; receiving a menu of selectable optionsfrom the transaction management system onto the mobile device, whereinthe menu of selectable options is presented as a Graphical UserInterface (GUI) menu on a display of the mobile device, and wherein thetransaction management system uses the token identifier to generate themenu of selectable options; and communicating transaction informationfrom the mobile device to the transaction management system, wherein thetransaction information includes one or more items selected from the GUImenu, wherein the mobile device is operated by a first entity, whereinthe token identifier is associated with a second entity that provides aservice to the first entity, wherein the second entity pre-configuresthe menu of selectable options on the transaction management systembefore the first entity activates the token identifier device using themobile device and communicates the token identifier from the mobiledevice to the transaction management system, wherein the tokenidentifier device is energized by the mobile device when the mobiledevice is within a pre-determined distance from the token identifierdevice and the mobile device outputs energy detected by the tokenidentifier device, wherein the token identifier device is not coupled toany dedicated power source, wherein the token identifier devicecomprises a memory, a processor, and an antenna, wherein the memorystores the token identifier, and wherein the antenna is used tocommunicate the token identifier stored in the memory.
 2. The method ofclaim 1, further comprising: receiving transaction confirmation from thetransaction management system, wherein the transaction confirmationindicates whether a payment from the first entity to the second entitysucceeded.
 3. The method of claim 1, wherein the GUI menu of selectableoptions include items provided by the second entity.
 4. The method ofclaim 1, further comprising: receiving order confirmation indicatingthat the second entity has completed preparing the selected menu itemsand also indicating that the first entity is able to pick up theselected menu items.
 5. The method of claim 1, wherein the onlyinformation communicated from the token identifier device to the mobiledevice is the token identifier.
 6. The method of claim 1, wherein thefirst entity is a first user, a customer, or an employee or contractorof the second entity, and wherein the second entity is a second user ora service provider.
 7. The method of claim 1, wherein the tokenidentifier device is a passive Near Field Communication (NFC) token. 8.A method comprising: energizing a token identifier device using a mobiledevice, wherein in response to energizing the token identifier device,the mobile device wirelessly obtains a token identifier stored in thetoken identifier device; communicating the token identifier from themobile device to a transaction management system; presenting a GraphicalUser Interface (GUI) menu of selectable options on the mobile device,wherein the transaction management system receives the token identifierfrom the mobile device, obtains selectable options using the tokenidentifier, and communicates to the mobile device the selectable optionsthat are presented via the GUI menu; detecting selection of one or moreitems presented via the GUI menu on the mobile device; and communicatingselected GUI menu items from the mobile device to the transactionmanagement system, wherein the mobile device is operated by a firstentity, wherein the token identifier is associated with a second entitythat provides a service to the first entity, wherein the second entitypre-configures the menu of selectable options on the transactionmanagement system before the first entity energizes the token identifierdevice using the mobile device and communicates the token identifierfrom the mobile device to the transaction management system, wherein thetoken identifier device is energized by the mobile device when themobile device is within a pre-determined distance from the tokenidentifier device and the mobile device outputs energy detected by thetoken identifier device, wherein the token identifier device is notcoupled to any dedicated power source, wherein the token identifierdevice comprises a memory, a processor, and an antenna, wherein thememory stores the token identifier, and wherein the antenna is used tocommunicate the token identifier stored in the memory.
 9. The method ofclaim 8, wherein the token identifier device is a passive Near FieldCommunication (NFC) token.
 10. The method of claim 8, furthercomprising: receiving transaction confirmation from the transactionmanagement system, wherein the transaction confirmation indicateswhether a payment from the first entity to the second entity succeeded.11. The method of claim 8, wherein the GUI menu of selectable optionsinclude items provided by the second entity.
 12. The method of claim 8,further comprising: receiving order confirmation indicating that thesecond entity has completed preparing the selected menu items and alsoindicating that the first entity is able to pick up the selected menuitems.
 13. The method of claim 8, wherein the first entity is a firstuser, a customer, or an employee or contractor of the second entity, andwherein the second entity is a second user or a service provider.
 14. Amethod comprising: activating a token identifier device using a mobiledevice, wherein in response to activating the token identifier device,the mobile device wirelessly obtains a token identifier stored in thetoken identifier device; communicating the token identifier from themobile device to a transaction management system; receiving a menu ofselectable options from the transaction management system onto themobile device, wherein the menu of selectable options is presented as aGraphical User Interface (GUI) menu on a display of the mobile device,and wherein the transaction management system uses the token identifierto generate the menu of selectable options; and communicatingtransaction information from the mobile device to the transactionmanagement system, wherein the transaction information includes one ormore items selected from the GUI menu, wherein the mobile device isoperated by a first entity, wherein the token identifier is associatedwith a second entity that provides a service to the first entity,wherein the second entity pre-configures the menu of selectable optionson the transaction management system before the first entity activatesthe token identifier device using the mobile device, wherein the tokenidentifier device is energized by the mobile device when the mobiledevice is within a distance from the token identifier device, whereinthe token identifier device is not coupled to any dedicated powersource, wherein the token identifier device comprises a memory, aprocessor, and an antenna, wherein the memory stores the tokenidentifier, and wherein the antenna is used to communicate the tokenidentifier stored in the memory.
 15. The method of claim 14, wherein thetoken identifier device is a passive Near Field Communication (NFC)token.
 16. The method of claim 14, further comprising: receivingtransaction confirmation from the transaction management system, whereinthe transaction confirmation indicates whether a payment from the firstentity to the second entity succeeded.
 17. The method of claim 14,wherein the GUI menu of selectable options include items provided by thesecond entity.
 18. The method of claim 14, further comprising: receivingorder confirmation indicating that the second entity has completedpreparing the selected menu items and also indicating that the firstentity is able to pick up the selected menu items.
 19. The method ofclaim 14, wherein the first entity is a first user, a customer, or anemployee or contractor of the second entity, and wherein the secondentity is a second user or a service provider.